![]() |
![]() |
![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
![]() |
To access the contents, click the chapter and section titles.
Oracle Performance Tuning and Optimization
Network ConsiderationsMake sure that your application will not exceed the bandwidth of the network. During testing, the load on the network is often much less than the load generated by real users. It is difficult (not to mention expensive and time consuming) to segment a network after the application has already been in production. Much testing is done on applications by loading the server with a small number of clients with a heavy workload. Although this arrangement can offer a lot of good data for tuning, remember that the system is stressed in a different way if you dont have a large number of users. In practice, you may find that you have to increase the number of dispatchers or tune some OS parameters to handle those additional connections. Performance Tuning after the System Is BuiltAfter the system is built, the job of tuning begins. In the design stage, you engineered performance into the system and you may have a good idea where the bottlenecks or hot spots might be. It is only after the system has been designed and built that you can really test your theories. If possible, generate user input in a laboratory environment and test the system for both stability and performance. It is difficult to generate large numbers of connectionsespecially in a client/server environmentbut if you can generate those connections, the results are worth it. In the testing stage, be sure to keep careful notes about any tuning you do and how those changes affect the system. Remember the five-step method discussed in Chapter 4, Tuning Methodology:
By following and sticking to an organized methodology, your results will be worthwhile. Remember that careful note-taking is a must. Tuning the ClientIn a client/server configuration, it is important to make sure that the client is not causing major delays. When using automated GUI application builders, you can sometimes forget that the application can be inefficient. Remember that not everyone in the corporation has the fastest PC on their desk, so optimize the application, if possible. The nice thing about tuning a client machine is that once it is tuned, it doesnt make any difference how many other machines are on the network. The client is still tuned. Even if you tune the server well, adding more connections can change the workload, making it necessary for you to tune the server again. Tuning the ServerThe server is the most complex aspect of system tuning. Consider that the server may serve hundreds or thousands of connections, that other activities may be occurring on the server, that you have to balance throughput and response times, and so on. Here are some of the factors to keep in mind when tuning the server:
Keep in mind that the server is a shared resource that must be tuned and balanced to serve the needs of all. Achieving this balance is not always easy. Part II of this book, Tuning the Server, addresses this topic in detail. Tuning the NetworkThere is really nothing you can do to tune the network per se. The network is a resource used by both the clients and the servers. You must make sure that the network does not exceed its limits; other than watching for network overload, the only thing to do is to add more resources (which usually means adding more or faster LAN segments). Although you cannot do anything to tune the network for more performance, you can tune your applications to make good use of the network. Under some operating systems, you can decrease network usage by carefully sizing the network packet size to more closely fit what SQL*Net wants. You can also reduce network consumption by not sending unnecessary data across the wire. The important thing is that the network does not cause excessive delays in response time or excessive processing in the clients or servers (caused by exceeding network limitations). If you have a problem, it may be time to upgrade the network.
|
![]() |
Products | Contact Us | About Us | Privacy | Ad Info | Home
Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc. All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited. |